{Spring} Fix previous error which hides the extension docs planned for deprecation#9112
{Spring} Fix previous error which hides the extension docs planned for deprecation#9112yuwzho wants to merge 5 commits intoAzure:mainfrom
Conversation
Added release notes for version 1.28.3.
|
| rule | cmd_name | rule_message | suggest_message |
|---|---|---|---|
| spring | sub group spring removed property deprecate_info_hide |
|
Hi @yuwzho, |
|
Thank you for your contribution! We will review the pull request and get back to you soon. |
There was a problem hiding this comment.
Pull Request Overview
This PR updates the Azure CLI Spring extension to show deprecation documentation by removing the hide=True parameter from the command group deprecation registration. The change makes the deprecation notice visible to users instead of hiding it.
- Version bump from 1.28.3 to reflect the change
- Modified deprecation registration to show the extension deprecation notice
- Updated history with release notes
Reviewed Changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| src/spring/setup.py | Version bump from 1.28.2 to 1.28.3 |
| src/spring/azext_spring/_breaking_change.py | Removed hide=True parameter to make deprecation notice visible |
| src/spring/HISTORY.md | Added release notes for version 1.28.3 |
|
The git hooks are available for azure-cli and azure-cli-extensions repos. They could help you run required checks before creating the PR. Please sync the latest code with latest dev branch (for azure-cli) or main branch (for azure-cli-extensions). pip install azdev --upgrade
azdev setup -c <your azure-cli repo path> -r <your azure-cli-extensions repo path>
|
CodeGen Tools Feedback CollectionThank you for using our CodeGen tool. We value your feedback, and we would like to know how we can improve our product. Please take a few minutes to fill our codegen survey |
|
github-actions
Bot
added
the
release-version-block
github-actions
Bot
removed
the
release-version-block
|
I suggest making a minor change rather than version change. Please wait my new PR. |
|
@zhoxing-ms , if the extension 1.28.2 is not released, I prefer to using PR #9113 to release 2 changes together. If the extension 1.28.2 has been released, I don't think we need to release a new version because #9113 is just for reference doc generation. Please help me double check. |
|
@dingmeng-xue Suggest using the 
|
Thanks. I created a PR to bump a patch version. #9113 |
calvinhzy
changed the title
This checklist is used to make sure that common guidelines for a pull request are followed.
Related command
General Guidelines
azdev style <YOUR_EXT>locally? (pip install azdevrequired)python scripts/ci/test_index.py -qlocally? (pip install wheel==0.30.0required)For new extensions:
About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update
src/index.jsonautomatically.You only need to update the version information in file setup.py and historical information in file HISTORY.rst in your PR but do not modify
src/index.json.